Skip to content

Decouple the JavaScript asset code from the report #3064

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 tasks done
danilocgsilva opened this issue Feb 25, 2025 · 3 comments
Open
2 tasks done

Decouple the JavaScript asset code from the report #3064

danilocgsilva opened this issue Feb 25, 2025 · 3 comments

Comments

@danilocgsilva
Copy link

Prerequisites

Description

The ability to generate a portable html as a report provides great convenience, but for each generated report includes a large Javascript code embedded within html.
When generating several reports, the total size required to have them becomes significantly large, and also turns into something impractical to integrate into certain projects.
It would be nice if instead of shipping all required scripts in a single inline javascript, the generated report imports the scripts from a CND, or at least, kept separate from html, so several reports could load the same script to render the information.

@danilocgsilva danilocgsilva changed the title Decouple the javascript assets code in the report Decouple the JavaScript asset code from the report Feb 26, 2025
@andrewbaldwin44
Copy link
Collaborator

Thanks for raising this issue @danilocgsilva. I'll try to take a look into improving this when I have a little more time

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 20 days.

@github-actions github-actions bot added the stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it label May 10, 2025
Copy link

This issue was closed because it has been marked stale for 20 days with no activity. This does not necessarily mean that the issue is bad, but it most likely means that nobody is willing to take the time to fix it. If you have found Locust useful, then consider contributing a fix yourself!

@cyberw cyberw reopened this May 30, 2025
@cyberw cyberw removed the stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it label May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants